The Ethereum consensus layer client side Prysm team released the post-mortem analysis report of the Fusaka mainnet failure, and Prysm experienced a network failure on December 4. During the event, almost all Prysm nodes experienced resource exhaustion while processing specific proofs, resulting in the inability to respond to validator requests in a timely manner. The failure affected the 411439th to 411480th epochs, with a total of 248 blocks lost in 42 epochs, a missing rate of 18.5%, a minimum...
以太坊共识层客户端 Prysm 团队发布 Fusaka 主网故障事后分析报告,Prysm 于 12 月 4 日发生网络故障。 事件期间,几乎所有 Prysm 节点在处理特定证明时遭遇资源耗尽,导致无法及时响应验证者请求。故障影响范围为第 411439 至 411480 epoch,共 42 个epoch内丢失 248 个区块,缺失率达 18.5%,网络参与率最低降至 75%,验证者损失约 382 ETH 的证明奖...
On December 4th, Lido officially issued a statement saying that after the successful completion of the Ethereum Fusaka hard fork, there was a vulnerability on the client side of the Prysm consensus layer, resulting in problems with network participation. The Lido protocol is running normally, and the pledger does not need to worry. Due to the distributed and decentralized nature of the verification node set at the bottom of the protocol, Lido was less affected by this incident, and the quick res...
12月4日消息,Lido 官方发文表示,以太坊 Fusaka 硬分叉顺利完成后,Prysm 共识层客户端出现漏洞,导致网络参与度出现问题。Lido 协议运行正常,质押者无需担心。由于协议底层的验证节点集分布式和去中心化的特性,Lido 受此事件影响较小,且 Prysm 客户端团队和节点运营商的快速响应有助于缓解问题。 Lido 团队与 Prysm 团队密切合作,...
The Ethereum Foundation said on the X platform that there is currently a problem with the Prysm consensus client side on the mainnet. If Prysm is being used, the CL node needs to be reconfigured. If another client side is being used, it is not affected and no action needs to be taken. Previously, it was reported that the Ethereum mainnet successfully activated the Fusaka upgrade, significantly enhancing data processing capabilities.
以太坊基金会在X平台表示,主网上的Prysm共识客户端目前存在问题。如果正在使用Prysm,需要重新配置CL节点。如果正在使用其他客户端,则不受影响,无需采取任何操作。 此前消息,以太坊主网成功激活Fusaka升级,大幅提升数据处理能力。
Ethereum protocol developer and Prysm maintainer Terence posted on the X platform that the Ethereum Core Developer Conference (AllCoreDevs) has reached a preliminary consensus to increase the blob target/maximum value from 3/6 to 6/9, and the specific implementation needs to be further tested and developed.
Terence, an Ethereum protocol developer and maintainer of Prysm, recently shared his views on Facebook, arguing that Ethereum's roadmap is simpler than many believe, and most of it can be achieved in the next four years: maximizing data availability, increasing censorship resistance, reducing trust through off-protocol block building and better time slot utilization, reaching consensus finalization faster, improving the staking user experience, finalizing the staking economy, limiting execution ...